DQ004 - Resolving Data Collection and Coding Questions
| DQ004 – Resolving Data Collection and Coding Questions | |
| Review Committee: Data | Start Date: 4/8/2005 |
| Attachments: None | Last Revised Date: 8/13/2025 |
| Forms: None | Last Reviewed Date: 02/11/2020 |
Introduction:
The TBIMS are committed to a process of systematic and timely resolution of data collection and coding questions. This will be done in order to: (1) provide a consistent data collection and coding methodology; 2) utilize a multidisciplinary approach; 3) allow for input from all stakeholders; and 4) maintain the highest level of data quality in the TBIMS National Database.
Purpose:
To establish procedures for assuring optimal and timely resolution of data collection and coding questions to maintain the highest level of data quality in the TBIMS National Database.
Scope:
Data Collection and/or coding questions related to the TBIMS National Database proposed by TBIMS staff.
Responsibilities:
The Data Collector and/or TBIMS where data collection and coding question has arisen will submit the question to the NDSC and the following procedural steps will be taken.
Procedural steps:
All questions about data collection or coding will be submitted to the NDSC, via email, phone, or Data listserv.
Local centers will not “hold” cases with pending questions but will code their problematic variables as “Unknown” and keep track of these cases and update them once the questions are resolved.
Within 5 business days of receiving a data collection or coding question, the NDSC will either answer the question or provide notification via the appropriate listserv(s) that satisfactory resolution of the question will require further steps.
Further steps are required to obtain satisfactory resolution of a question when either:
The NDSC does not have the expertise needed to answer the question, or
Resolving the question involves changes to the syllabus that require TBIMS approval. (See SOP OP002 – Procedure for Implementing Changes to Database)
In cases where the NDSC does not have the expertise needed to answer a question:
The question will be forwarded to the Data Committee Chair within 5 business days and the originator of the question will be cc’d as notification of the status of the question.
If within 10 business days the Data Committee is unable to develop an answer to the question, the Chair will immediately forward the question via email to the “Databusters” and the originator of the question will be cc’d as notification of the status of the question. As of 11/2024, the Medical Databusters are: Dmitry Esterov (MN), Flora Hammond (IN), and Nancy Chiaravalloti (NJ-Kessler); the BTACT Databusters are: Kristen Dams-O’Connor (NY-Mt. Sinai), Amanda Rabinowitz (PA-Moss), Brittany Engelman (NY-Mt. Sinai), Marc Silva (Tampa-VA PRC), and Anthony Lequerica (NJ-Kessler).
If within 10 business days the Databusters are unable to develop an answer to the question, they will immediately notify the Data Committee Chair to seek assistance from persons within and/or external to the TBIMS. They will then obtain an answer within 10 business days and notify the NDSC of the answer.
The NDSC will forward the answer to the originator of the question within 5 business days of receiving it from the Data Committee.
Answers requiring revisions to the syllabus will follow SOP 603b – Procedure for Implementing Changes to Database.
Training requirements:
None
Compliance:
All TBIMS centers, longitudinal follow-up centers and the NDSC will comply with this procedure.
References:
None
History:
| Date | Action |
|---|---|
| 4/8/2005 | Version used to create this SOP |
| 9 /16/2008 | Transferred to SOP template |
| 12 /12/2008 | SOP Review Committee Recommended moving sections related to changes to the national database syllabus to SOP 603b – Procedure for Implementing Changes to Database Approved by SOP Review Committee then by Planning Committee and Project Directors |
| 09 /08/2014 | SOP Reviewed |
| 02 /11/2020 | SOP Reviewed |
| 11 /14/2024 | Databuster members updated |
| 8 /13/2025 | Databuster members updated |
Review Schedule:
At least every 5 years.